Smart network interface controller certificate management

ABSTRACT

An information handling system may include a management controller configured to provide out-of-band management of the information handling system, and a network interface controller comprising a network interface controller storage resource. The management controller may be configured to: receive, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and transmit the at least one signature to the network interface controller. The network interface controller may be configured to install the network interface OS to the network interface controller storage resource based on the at least one signature.

TECHNICAL FIELD

The present disclosure relates in general to information handling systems, and more particularly to methods and systems for managing cryptographic certificates in a smart network interface controller.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

In some computing applications, an information handling system may include a hypervisor for hosting one or more virtual resources such as virtual machines (VMs). A hypervisor may comprise software and/or firmware generally operable to allow multiple virtual machines and/or operating systems to run on a single information handling system at the same time. This operability is generally allowed via virtualization, a technique for hiding the physical characteristics of computing system resources (e.g., physical hardware of the computing system) from the way in which other systems, applications, or end users interact with those resources. Thus, a virtual machine may comprise any program of executable instructions, or aggregation of programs of executable instructions, configured to execute a guest operating system on a hypervisor or host operating system in order to act through or in connection with the hypervisor/host operating system to manage and/or control the allocation and usage of hardware resources such as memory, central processing unit time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted by the guest operating system.

Hyper-converged infrastructure (HCI) is one IT framework that combines storage, computing, and networking into a single system in an effort to reduce data center complexity and increase scalability. Hyper-converged platforms may include a hypervisor for virtualized computing, software-defined storage, and virtualized networking, and they typically run on standard, off-the-shelf servers. One type of HCI solution is the Dell EMC VxRail™ system. Some examples of HCI systems may operate in various environments (e.g., an HCI management system such as the VMware® vSphere® environment, which may include ESXi™ and vCenter™ components, or any other HCI management system).

In other applications, an information handling system may be used in a “bare metal” configuration in which only one operating system is installed, and the hypervisor and virtual resources are not needed.

In either scenario, a network interface of the information handling system may comprise a smart network interface card or “SmartNIC” and/or a data processing unit (DPU), which may offer capabilities not found in traditional NICs. For purposes of this disclosure, the terms “SmartNIC” and “DPU” may be used interchangeably. Further, it should be noted that some embodiments may operate on devices other than SmartNICs. For example, graphics processing units (GPUs), infrastructure processing units (IPUs), and other types of accelerators and smart devices may benefit from the teachings of this disclosure. For the sake of clarity and concreteness, the SmartNIC example will be discussed in detail herein, but one of ordinary skill in the art with the benefit of this disclosure will understand its application to such other devices.

A SmartNIC may act as a system within a system, including its own Unified Extensible Firmware Interface Basic Input/Output System (UEFI BIOS), its own operating system (OS) such as ESXio or any other suitable OS, and/or its own management controller such as a baseboard management controller (BMC).

In some implementations, cryptographic certificates for a SmartNIC (e.g., Secure Boot certificates) may be managed by a management controller. The ability to install and boot a particular SmartNIC OS may be enabled or disabled by the presence or absence, respectively, of a certificate from the supplier of that OS. For example, certificates may be stored in a certificate database on the management controller and a corresponding database on the SmartNIC, and it may be desirable to keep such databases in sync.

However, various problems may arise. For example, when an updated set of Secure Boot certificates is available, in some situations a system's management controller may be offline or otherwise unavailable. Thus the SmartNIC Secure Boot certificates may not be updated, which may result in outdated and/or incompatible certificates. Further, it can be a burden for a user to manually configure the Secure Boot certificates for a SmartNIC based on the SmartNIC OS type and/or version that is installed, based on the SmartNIC hardware vendor, etc. Still further, in the case of a replacement SmartNIC being installed, the Secure Boot certificates may need to be re-provisioned to the new device.

Accordingly, embodiments of this disclosure may provide simplified management solutions that address these and other problems.

The example of UEFI Secure Boot signatures is discussed in detail herein for the sake of concreteness and clarity. One of ordinary skill in the art with the benefit of this disclosure will understand its applicability to other types of certificates and signatures as well. Further, for purposes of this disclosure, the terms “certificate” and “signature” may be used interchangeably.

It should be noted that the discussion of a technique in the Background section of this disclosure does not constitute an admission of prior-art status. No such admissions are made herein, unless clearly and unambiguously identified as such.

SUMMARY

In accordance with the teachings of the present disclosure, the disadvantages and problems associated with certificate management on a SmartNIC may be reduced or eliminated.

In accordance with embodiments of the present disclosure, an information handling system may include a management controller configured to provide out-of-band management of the information handling system, and a network interface controller comprising a network interface controller storage resource. The management controller may be configured to: receive, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and transmit the at least one signature to the network interface controller. The network interface controller may be configured to install the network interface OS to the network interface controller storage resource based on the at least one signature.

In accordance with these and other embodiments of the present disclosure, a method may include, in an information handling system including a management controller and a network interface controller that includes a network interface controller storage resource: the management controller receiving, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and the management controller transmitting the at least one signature to the network interface controller; and the network interface controller installing the network interface OS to the network interface controller storage resource based on the at least one signature.

In accordance with these and other embodiments of the present disclosure, an article of manufacture may include a non-transitory, computer-readable medium having instructions thereon that are executable by at least one processor of a management controller of an information handling system for: receiving, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and transmitting the at least one signature to the network interface controller; wherein the network interface controller is configured to install the network interface OS to a network interface controller storage resource thereof based on the at least one signature.

Technical advantages of the present disclosure may be readily apparent to one skilled in the art from the figures, description and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.

It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

FIG. 1 illustrates a block diagram of selected components of an example information handling system, in accordance with embodiments of the present disclosure; and

FIG. 2 illustrates a block diagram of selected components of an example information handling system, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

Preferred embodiments and their advantages are best understood by reference to FIGS. 1 and 2 , wherein like numbers are used to indicate like and corresponding parts.

For the purposes of this disclosure, the term “information handling system” may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (“CPU”) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input/output (“I/O”) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

For purposes of this disclosure, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected directly or indirectly, with or without intervening elements.

When two or more elements are referred to as “coupleable” to one another, such term indicates that they are capable of being coupled together.

For the purposes of this disclosure, the term “computer-readable medium” (e.g., transitory or non-transitory computer-readable medium) may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing. Physical computer-readable media such as disk drives, solid-state drives, non-volatile memory, etc. may also be referred to herein as “physical storage resources.”

For the purposes of this disclosure, the term “information handling resource” may broadly refer to any component system, device, or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems, buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, and/or any other components and/or elements of an information handling system.

For the purposes of this disclosure, the term “management controller” may broadly refer to an information handling system that provides management functionality (typically out-of-band management functionality) to one or more other information handling systems. In some embodiments, a management controller may be (or may be an integral part of) a service processor, a baseboard management controller (BMC), a chassis management controller (CMC), or a remote access controller (e.g., a Dell Remote Access Controller (DRAC) or Integrated Dell Remote Access Controller (iDRAC)).

FIG. 1 illustrates a block diagram of selected components of an example information handling system 100 having a plurality of host systems 102, in accordance with embodiments of the present disclosure. As shown in FIG. 1 , information handling system 100 may include a plurality of host systems 102 coupled to one another via an internal network 110.

In some embodiments, information handling system 100 may include a single chassis housing a plurality of host systems 102. In other embodiments, information handling system 100 may include a cluster of multiple chassis, each with one or more host systems 102. In yet other embodiments, host systems 102 may be entirely separate information handling systems, and they may be coupled together via an internal network or an external network such as the Internet.

In some embodiments, a host system 102 may comprise a server (e.g., embodied in a “sled” form factor). In these and other embodiments, a host system 102 may comprise a personal computer. In other embodiments, a host system 102 may be a portable computing device (e.g., a laptop, notebook, tablet, handheld, smart phone, personal digital assistant, etc.). As depicted in FIG. 1 , information handling system 100 may include a processor 103, a memory 104 communicatively coupled to processor 103, and a network interface 106 communicatively coupled to processor 103. For the purposes of clarity and exposition, in FIG. 1 , each host system 102 is shown as comprising only a single processor 103, single memory 104, and single network interface 106. However, a host system 102 may comprise any suitable number of processors 103, memories 104, and network interfaces 106.

A processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, processor 103 may interpret and/or execute program instructions and/or process data stored in a memory 104 and/or other computer-readable media accessible to processor 103.

A memory 104 may be communicatively coupled to a processor 103 and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). A memory 104 may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 100 is turned off.

As shown in FIG. 1 , a memory 104 may have stored thereon a hypervisor 116 and one or more guest operating systems (OS) 118. In some embodiments, hypervisor 116 and one or more of guest OSes 118 may be stored in a computer-readable medium (e.g., a local or remote hard disk drive) other than a memory 104 which is accessible to processor 103. Each guest OS 118 may also be referred to as a “virtual machine.”

A hypervisor 116 may comprise software and/or firmware generally operable to allow multiple virtual machines and/or operating systems to run on a single computing system (e.g., an information handling system 100) at the same time. This operability is generally allowed via virtualization, a technique for hiding the physical characteristics of computing system resources (e.g., physical hardware of the computing system) from the way in which other systems, applications, or end users interact with those resources. A hypervisor 116 may be one of a variety of proprietary and/or commercially available virtualization platforms, including without limitation, VIRTUALLOGIX VLX FOR EMBEDDED SYSTEMS, IBM's Z/VM, XEN, ORACLE VM, VMWARE's ESX SERVER, L4 MICROKERNEL, TRANGO, MICROSOFT's HYPER-V, SUN's LOGICAL DOMAINS, HITACHI's VIRTAGE, KVM, VMWARE SERVER, VMWARE WORKSTATION, VMWARE FUSION, QEMU, MICROSOFT's VIRTUAL PC and VIRTUAL SERVER, INNOTEK's VIRTUALBOX, and SWSOFT's PARALLELS WORKSTATION and PARALLELS DESKTOP.

In one embodiment, a hypervisor 116 may comprise a specially-designed OS with native virtualization capabilities. In another embodiment, a hypervisor 116 may comprise a standard OS with an incorporated virtualization component for performing virtualization.

In another embodiment, a hypervisor 116 may comprise a standard OS running alongside a separate virtualization application. In this embodiment, the virtualization application of the hypervisor 116 may be an application running above the OS and interacting with computing system resources only through the OS. Alternatively, the virtualization application of a hypervisor 116 may, on some levels, interact indirectly with computing system resources via the OS, and, on other levels, interact directly with computing system resources (e.g., similar to the way the OS interacts directly with computing system resources, or as firmware running on computing system resources). As a further alternative, the virtualization application of a hypervisor 116 may, on all levels, interact directly with computing system resources (e.g., similar to the way the OS interacts directly with computing system resources, or as firmware running on computing system resources) without utilizing the OS, although still interacting with the OS to coordinate use of computing system resources.

As stated above, a hypervisor 116 may instantiate one or more virtual machines. A virtual machine may comprise any program of executable instructions, or aggregation of programs of executable instructions, configured to execute a guest OS 118 in order to act through or in connection with a hypervisor 116 to manage and/or control the allocation and usage of hardware resources such as memory, CPU time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted by the guest OS 118. In some embodiments, a guest OS 118 may be a general-purpose OS such as WINDOWS or LINUX, for example. In other embodiments, a guest OS 118 may comprise a specific- and/or limited-purpose OS, configured so as to perform application-specific functionality (e.g., persistent storage).

At least one host system 102 in information handling system 100 may have stored within its memory 104 a virtual machine manager 120. A virtual machine manager 120 may comprise software and/or firmware generally operable to manage individual hypervisors 116 and the guest OSes 118 instantiated on each hypervisor 116, including controlling migration of guest OSes 118 between hypervisors 116. Although FIG. 1 shows virtual machine manager 120 instantiated on a host system 102 on which a hypervisor 116 is also instantiated, in some embodiments virtual machine manager 120 may be instantiated on a dedicated host system 102 within information handling system 100, or a host system 102 of another information handling system 100.

A network interface 106 may include any suitable system, apparatus, or device operable to serve as an interface between an associated information handling system 100 and internal network 110. A network interface 106 may enable its associated information handling system 100 to communicate with internal network 110 using any suitable transmission protocol (e.g., TCP/IP) and/or standard (e.g., IEEE 802.11, Wi-Fi). In certain embodiments, a network interface 106 may include a physical network interface card (NIC). In the same or alternative embodiments, a network interface 106 may be configured to communicate via wireless transmissions. In the same or alternative embodiments, a network interface 106 may provide physical access to a networking medium and/or provide a low-level addressing system (e.g., through the use of Media Access Control addresses). In some embodiments, a network interface 106 may be implemented as a local area network (“LAN”) on motherboard (“LOM”) interface. A network interface 106 may comprise one or more suitable NICs, including without limitation, mezzanine cards, network daughter cards, etc.

In some embodiments, a network interface 106 may comprise a SmartNIC and/or a DPU. In addition to the stateful and custom offloads a SmartNIC or DPU may provide, it may have an independent management domain with a separate operating system, independent credentials, and independent remote access. Accordingly, network interface 106 may include its own specialized processor and memory.

In addition to processor 103, memory 104, and network interface 106, a host system 102 may include one or more other information handling resources.

Internal network 110 may be a network and/or fabric configured to communicatively couple information handling systems to each other. In certain embodiments, internal network 110 may include a communication infrastructure, which provides physical connections, and a management layer, which organizes the physical connections of host systems 102 and other devices coupled to internal network 110. Internal network 110 may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, the Internet or any other appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data). Internal network 110 may transmit data using any storage and/or communication protocol, including without limitation, Fibre Channel, Fibre Channel over Ethernet (FCoE), Small Computer System Interface (SCSI), Internet SCSI (iSCSI), Frame Relay, Ethernet Asynchronous Transfer Mode (ATM), Internet protocol (IP), or other packet-based protocol, and/or any combination thereof. Network 110 and its various components may be implemented using hardware, software, or any combination thereof.

As discussed above, embodiments of this disclosure may provide techniques for provisioning SmartNIC Secure Boot certificates by a management controller.

Turning now to FIG. 2 , a block diagram of selected components of an information handling system 200 is shown, according to some embodiments. Information handling system 200 may include a host system (not shown), a management controller 212, and one or more SmartNICs 206. The host system may be coupled to the hardware of SmartNICs 206 via a communication channel such as Peripheral Component Interconnect Express (PCIe) in some embodiments. System 200 may further be communicatively coupled to a management platform 250. In general, management platform 250 may include any external management platform for managing information handling systems such as information handling system 200. In one implementation, management platform 250 may include an HCI management system such as vCenter, vSphere, etc. In other implementations, management platform 250 may be a non-HCI management system.

As shown, management platform 250 may include Secure Boot certificate stores 1 through N, and it may provision management controller 212 with any suitable subset of such stores. For example, in the embodiment shown, management controller 212 has been provisioned with stores 1 and 2 only, which include the certificates that are appropriate based on the characteristics of SmartNICs 206.

Management controller 212 may be coupled to SmartNICs 206 via a network controller sideband interface (NC-SI), which may be established over reduced media-independent interface (RMII) based transport (RBT), over PCIe vendor-defined message (VDM), over SMBus, etc.

Management controller 212 may have the ability to perform automatic certificate enrollment (e.g., Active Directory automatic certificate enrollment), which may also be used to manage Secure Boot certificates for SmartNICs 206 based on information from management platform 250.

SmartNIC Secure Boot certificates may be managed in a centralized SmartNIC UEFI signature data store at management platform 250. Management platform 250 may configure the Secure Boot profiles mapped to a particular SmartNIC 206 based on the combination of the management system version for information handling system 200, the SmartNIC OS version for SmartNIC 206, the SmartNIC vendor identifier for SmartNIC 206, a hardware architecture identifier for SmartNIC 206, and/or any other relevant information. Management platform 250 may then inject Secure Boot profile IDs and policies to management controller 212, which may be mapped onto individual ones of SmartNICs 206 as appropriate. Based on the configured policies, management controller 212 may automatically renew the SmartNIC Secure Boot certificates using the automatic certificate enrollment feature.

Further, when a previously offline management controller 212 becomes online, it may sync with management platform 250 to retrieve the associated SmartNIC Secure Boot certificates, storing them locally, and then causing SmartNIC 206 to reboot so that its local store may be updated.

In one embodiment, Secure Boot certificate management may be centralized in management platform 250, which may implement an Allow list and a Deny list of Secure Boot certificates for SmartNICs 206. Management platform 250 may manage the Secure Boot profiles mapped with the combination of valid Secure Boot certificates. Management platform 250 may then transmit the Secure Boot profiles and policies to management controller 212.

In one embodiment, SmartNICs 206 may each publish information regarding their SmartNIC OS version, hardware architecture identifier, etc. by using a DHCPv6 solicit message. Based on the configured policy, management controller 212 may then automatically renew the Secure Boot certificates for each SmartNIC 206 by using automatic certificate enrollment based on the published information.

Management controller 212 may further query the capabilities of each SmartNIC 206 (e.g., presence or absence of a real-time clock (RTC), etc.) for use in managing Secure Boot certificates. Management controller 212 may then perform validity checks of the Secure Boot certificates on behalf of SmartNICs 206 (e.g., verifying the validity and expiration of signatures, etc.), ensuring that all SmartNICs 206 have updated and confirming Secure Boot certificates.

Accordingly, embodiments of this disclosure allow for a management controller to handle the management of Secure Boot certificates for one or more SmartNICs. Secure Boot certificates may be upgraded (e.g., by adding, deleting, and/or replacing certificates) via the management controller by making changes at a centralized management platform.

Although various possible advantages with respect to embodiments of this disclosure have been described, one of ordinary skill in the art with the benefit of this disclosure will understand that in any particular embodiment, not all of such advantages may be applicable. In any particular embodiment, some, all, or even none of the listed advantages may apply.

This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.

Unless otherwise specifically noted, articles depicted in the drawings are not necessarily drawn to scale. However, in some embodiments, articles depicted in the drawings may be to scale.

Further, reciting in the appended claims that a structure is “configured to” or “operable to” perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) for that claim element. Accordingly, none of the claims in this application as filed are intended to be interpreted as having means-plus-function elements. Should Applicant wish to invoke § 112(f) during prosecution, Applicant will recite claim elements using the “means for [performing a function]” construct.

All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present inventions have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure. 

What is claimed is:
 1. An information handling system comprising: a management controller configured to provide out-of-band management of the information handling system; and a network interface controller comprising a network interface controller storage resource; wherein the management controller is configured to: receive, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and transmit the at least one signature to the network interface controller; and wherein the network interface controller is configured to install the network interface controller OS to the network interface controller storage resource based on the at least one signature.
 2. The information handling system of claim 1, wherein the network interface is a SmartNIC.
 3. The information handling system of claim 1, wherein the at least one signature is a Secure Boot signature.
 4. The information handling system of claim 1, wherein the management controller is further configured to select the at least one signature based on characteristics of the network interface controller.
 5. The information handling system of claim 4, wherein the characteristics comprise at least a vendor identifier and a hardware architecture identifier associated with the network interface controller.
 6. The information handling system of claim 1, wherein the management controller is further configured to verify that the at least one signature is valid.
 7. A method comprising, in an information handling system including a management controller configured to provide out-of-band management of the information handling system and a network interface controller that includes a network interface controller storage resource: the management controller receiving, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and the management controller transmitting the at least one signature to the network interface controller; and the network interface controller installing the network interface OS to the network interface controller storage resource based on the at least one signature.
 8. The method of claim 7, wherein the network interface controller is a SmartNIC.
 9. The method of claim 7, wherein the at least one signature is a Secure Boot signature.
 10. The method of claim 7, further comprising the management controller selecting the at least one signature based on characteristics of the network interface controller.
 11. The method of claim 10, wherein the characteristics comprise at least a vendor identifier and a hardware architecture identifier associated with the network interface controller.
 12. The method of claim 7, further comprising the management controller verifying that the at least one signature is valid.
 13. An article of manufacture comprising a non-transitory, computer-readable medium having instructions thereon that are executable by at least one processor of a management controller of an information handling system for: receiving, from a centralized management platform, information regarding at least one signature associated with a network interface controller operating system (OS) configured to be executed by the network interface controller; and transmitting the at least one signature to the network interface controller; wherein the network interface controller is configured to install the network interface OS to a network interface controller storage resource thereof based on the at least one signature.
 14. The article of claim 13, wherein the network interface controller is a SmartNIC.
 15. The article of claim 13, wherein the at least one signature is a Secure Boot signature.
 16. The article of claim 13, wherein the instructions are further executable for selecting the at least one signature based on characteristics of the network interface controller.
 17. The article of claim 16, wherein the characteristics comprise at least a vendor identifier and a hardware architecture identifier associated with the network interface controller.
 18. The article of claim 13, wherein the instructions are further executable for: verifying that the at least one signature is valid. 